home *** CD-ROM | disk | FTP | other *** search
- Path: keats.ugrad.cs.ubc.ca!not-for-mail
- From: c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku)
- Newsgroups: comp.lang.c
- Subject: Re: Trace C memory allocation
- Date: 14 Apr 1996 18:45:08 -0700
- Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
- Message-ID: <4ks9n4INNi1j@keats.ugrad.cs.ubc.ca>
- References: <4ks3n2$2mt@news.hklink.net>
- NNTP-Posting-Host: keats.ugrad.cs.ubc.ca
-
- In article <4ks3n2$2mt@news.hklink.net>, Alex Chu <alex@station.net> wrote:
- >
- >Hi everybody,
- >
- >
- > I using the Turbo C 2.0 for DOS at this moment. I wonder that how can
- >I trace the memory allocation in C. The 'Add Watch' option only can
-
- Easy! An allocation block can't hide anywhere---it has to be somewhere inside a
- 640,000 byte region. That makes things easy. Just go into DEBUG.COM and grep
- the memory for the likely start of a malloc chunk.
-